test(cli): add --help case to config snap tests for npm10/yarn1/yarn4#1585
Merged
fengmk2 merged 2 commits intoMay 15, 2026
Merged
Conversation
Aligns these three fixtures with the existing pnpm10/pnpm11 config snaps, which already verify clap's `--help` output. Provides a deterministic regression signal for the `vp pm config` command surface across the full PM matrix.
✅ Deploy Preview for viteplus-preview canceled.
|
fengmk2
approved these changes
May 15, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Align the
vp pm configsnap matrix by adding a--helpcase tocommand-config-npm10,command-config-yarn1, andcommand-config-yarn4— previously onlybun,pnpm10, andpnpm11captured it.clap-generated help is deterministic, so this gives a cheap regression signal whenever the
vp pm configcommand surface (flags, descriptions, ordering) changes, and forces every PM fixture to flag the same regression in lockstep.Changes
For each of the three fixtures:
steps.json: prependvp pm config --helpahead of the existing--dry-runstepsnap.txt: regenerated with the 17-line help block; existingset/get/deleteoutput unchanged